Note: As mentioned in the "proposal doc", moving the docs repo into angular/components has various benefits. Long-term we should do this, or as a follow-up. The PR is conceptually ready for review, just contains some testing TODOs still.

I chatted about this to a good extent with @gkalpak. Long-term we certainly want to share the same script from AIO, and potentially also use redirects (e.g. where rc.angular.io would just redirect to angular.io if there is no RC -- but that is out of scope for now). The current changes include:

• A TS-converted, reduced conceptual replica of the angular/angular script -- but leveraging @angular/dev-infra-private instead of manually consulting Git for release train info.
• Logic for cloning the docs-repo (no caching for now; seems fast enough), and running monitoring tests as a cronjob to ensure material.angular.io remains working (we don't have any good integration tests..)
• Preparation logic for having docs-app snapshots for every commit (using preview channel deployments)

@josephperrott addressed your feedback and also tested on my fork again. We'll also need a patch-port

Note: Corresponding patch PR that needs to go in once this gets merged: #24552

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}